Problem Note 39481: "RemoteException occurred in server thread" error occurs when choosing a Recipient List Type of CI Export Definition in SAS® Digital Marketing Studio
When using the SAS Digital Marketing Studio Create E-mail Broadcast wizard, a "RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException" error occurs if a Recipient List Type of CI Export Definition is chosen and the SAS Customer Intelligence Core is deployed in JBoss.
To resolve this problem, save this file to your machine, unzip its contents, and then follow these steps on the middle-tier server:
UNIX:
- Copy SASCustIntellCore5.3.ear from Staging to a temporary location (mkdir /tmp/core; cp SASCustIntellCore5.3.ear /tmp/core).
- Explode the EAR file (cd /tmp/core; jar xvf SASCustIntellCore5.3.ear).
- Copy the jboss-app.xml file that is displayed to META-INF (cp /wherever/jboss-app.xml META-INF).
- Create a directory for the exploded WAR file (mkdir war).
- From the new directory, explode the WAR file (cd war; jar xvf ../sas.core.ci.webservices.war).
- Remove the two JAR files from the WAR file (rm WEB-INF/lib/*.jar).
- Copy the delivered manifest to the WAR file (cp –f /wherever/MANIFEST.MF META-INF).
- Rewrap the WAR file (jar cvf ws.war *).
- Move the new version of the WAR file on top of the old version (mv ws.war ../sas.core.ci.webservices.war).
- Remove the WAR file and META-INF directories that were added in Steps 3 and 8 (cd ..; rm –r war).
- Build a new version of the EAR file (rm SASCustIntellCore5.3.ear; jar cvf SASCustIntellCore5.3.ear *).
- Copy the new EAR file to your staging area.
- Copy the new EAR file to the JBoss deploy_sas directory.
Windows:
- Copy sas.custintellcore5.3ear from Staging (…Lev1\Web\Staging) to a temporary location (C:\temp\core)
- Rename the EAR file as a ZIP file sas.custintellcore5.3.zip
- Unzip the sas.custintellcore5.3.zip to C:\temp\core
- Copy the jboss-app.xml file that was downloaded and unzipped to C:\temp\core\META-INF.
- Create a folder into which you will unzip the sas.core.ci.webservices.war (C:\temp\core\war).
- Rename the C:\temp\core\sas.core.ci.webservices.war to sas.core.ci.webservices.zip.
- Unzip the sas.core.ci.webservices.zip file into the new C:\temp\core\war.
- Delete the two JAR files from C:\temp\core\war\WEB-INF\lib.
- Copy the MANIFEST.MF that was downloaded and unzipped to C:\temp\core\war\META-INF.
- Delete C:\temp\core\sas.core.ci.webservices.zip.
- Zip the contents of the C:\temp\core\war into sas.core.ci.webservices.zip.
- Rename sas.core.ci.webservices.zip as sas.core.ci.webservices.war.
- Copy sas.core.ci.webservices.war to C:\temp\core.
- Delete the C:\temp\core\war folder (all subfolders and contents).
- Delete the original zipped version of the EAR file (C:\temp\core\sas.custintellcore5.3.zip).
- Zip the contents of C:\temp\core into sas.custintellcore5.3.zip.
- Rename sas.custintellcore5.3.zip to sas.custintellcore5.3.ear.
- Copy the new EAR file to your staging area, (from C:\temp\core\sas.custintellcore5.3.ear to …Lev1\Web\Staging\sas.custintellcore5.3.ear).
- Copy the new EAR file to the JBoss deploy_sas directory.
Operating System and Release Information
SAS System | SAS Digital Marketing Studio | Linux | 5.3 | | 9.2 TS2M2 | |
SAS System | SAS Digital Marketing | Microsoft Windows Server 2003 Enterprise Edition | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Datacenter Edition | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Standard Edition | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 for x64 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2008 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2008 for x64 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows XP Professional | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows 7 Enterprise 32 bit | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows 7 Enterprise x64 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows 7 Home Premium 32 bit | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows 7 Home Premium x64 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows 7 Professional 32 bit | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows 7 Professional x64 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows 7 Ultimate 32 bit | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows 7 Ultimate x64 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows Vista | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Windows Vista for x64 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
64-bit Enabled AIX | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
64-bit Enabled HP-UX | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
64-bit Enabled Solaris | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
HP-UX IPF | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Linux | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
Solaris for x64 | 5.3_M3 | 5.4 | 9.2 TS2M3 | 9.2 TS2M3 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | alert |
Date Modified: | 2012-01-23 15:04:05 |
Date Created: | 2010-04-28 17:40:32 |